Skip to content

Conversation

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from bf5e0d2 to c42a0e8 Compare October 6, 2025 19:22
updates:
- https://github.com/psf/blackhttps://github.com/psf/black-pre-commit-mirror
- [github.com/psf/black-pre-commit-mirror: 25.1.0 → 25.9.0](psf/black-pre-commit-mirror@25.1.0...25.9.0)
- [github.com/tox-dev/pyproject-fmt: v2.6.0 → v2.10.0](tox-dev/pyproject-fmt@v2.6.0...v2.10.0)
- [github.com/PyCQA/isort: 6.0.1 → 7.0.0](PyCQA/isort@6.0.1...7.0.0)
- [github.com/asottile/pyupgrade: v3.20.0 → v3.21.0](asottile/pyupgrade@v3.20.0...v3.21.0)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from c42a0e8 to 43c9066 Compare October 13, 2025 18:54
@JanFSchulte
Copy link
Contributor

Looks like after these version bumps, pre-commit tries to add support for python 3.14 to the pyproject.toml. Is that something we want?

updates:
- https://github.com/psf/blackhttps://github.com/psf/black-pre-commit-mirror
- [github.com/psf/black-pre-commit-mirror: 25.1.0 → 25.9.0](psf/black-pre-commit-mirror@25.1.0...25.9.0)
- [github.com/tox-dev/pyproject-fmt: v2.6.0 → v2.11.0](tox-dev/pyproject-fmt@v2.6.0...v2.11.0)
- [github.com/PyCQA/isort: 6.0.1 → 7.0.0](PyCQA/isort@6.0.1...7.0.0)
- [github.com/asottile/pyupgrade: v3.20.0 → v3.21.0](asottile/pyupgrade@v3.20.0...v3.21.0)
- [github.com/mgedmin/check-manifest: 0.50 → 0.51](mgedmin/check-manifest@0.50...0.51)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 43c9066 to 0281426 Compare October 20, 2025 20:53
@JanFSchulte JanFSchulte merged commit a57be2a into main Oct 31, 2025
4 checks passed
@JanFSchulte JanFSchulte deleted the pre-commit-ci-update-config branch October 31, 2025 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants